ci is all red probably due to this change

ci is all red probably due to this change

@VincentLanglet @soyuka At some points both Collection and iterable types are used from different places for the same property, so I found a solution to prevent typing error from PHPStan, here an example.
WDYT?

Otherwise I have this strange failure in Behat checks but I only edited fixtures files (entities & documents), any idea?

@VincentLanglet @soyuka At some points both Collection and iterable types are used from different places for the same property, so I found a solution to prevent typing error from PHPStan, here an example.

WDYT?

I feel like it's really hacky and kinda a code smell to have an "addFoo" method which does nothing when the property is an iterable.

Ok it's "only for tests files" but it could still lead to some weird error in the futur, and adding such hack just to fix a phpstan baseline error might not be worth it.

Otherwise I have this strange failure in Behat checks but I only edited fixtures files (entities & documents), any idea?

It could be more insteresting to use the first fix you use (Collection everywhere) and understand the behat failure. I can only take a look starting next week since i'm currently one vacation without a computer.

@VincentLanglet @soyuka At some points both Collection and iterable types are used from different places for the same property, so I found a solution to prevent typing error from PHPStan, here an example.

WDYT?

I feel like it's really hacky and kinda a code smell to have an "addFoo" method which does nothing when the property is an iterable.

Ok it's "only for tests files" but it could still lead to some weird error in the futur, and adding such hack just to fix a phpstan baseline error might not be worth it.

Otherwise I have this strange failure in Behat checks but I only edited fixtures files (entities & documents), any idea?

It could be more insteresting to use the first fix you use (Collection everywhere) and understand the behat failure. I can only take a look starting next week since i'm currently one vacation without a computer.

Ok thanks @VincentLanglet , I will revert to Collection everywhere, but probably we'll need to adapt some parts which uses iterables at some parts.